Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1084

reference
395-tree-1
name
1084
tree-preservation-order

undefined

395-tpo-1
uprn
address-text
point
POINT (-1.037507 50.895393)
geometry
MULTIPOLYGON (((-1.037450 50.895387,-1.037452 50.895398,-1.037460 50.895409,-1.037473 50.895417,-1.037488 50.895422,-1.037506 50.895424,-1.037523 50.895422,-1.037539 50.895417,-1.037552 50.895409,-1.037560 50.895399,-1.037563 50.895388,-1.037561 50.895377,-1.037553 50.895367,-1.037541 50.895359,-1.037525 50.895354,-1.037507 50.895352,-1.037490 50.895353,-1.037474 50.895358,-1.037461 50.895366,-1.037453 50.895376,-1.037450 50.895387)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL